Modifications of headend forwarding rules to join wide area network branch hosts to multicast groups

ABSTRACT

In an example, a system is described which includes a centralized controller, a first agent controller, and a second agent controller. The centralized controller executes a routing application to control routing of network traffic across links of a wide area network. The first agent controller is deployed at a branch location of the wide area network to notify the routing application when a host at the branch location requests membership in a multicast group. The second agent controller is deployed at a headend of the wide area network to modify a forwarding rule in response to an instruction from the routing application. The forwarding rule controls an interaction between the headend location and an upstream router to redirect network traffic associated with the multicast group in a manner that joins the host to the multicast group.

BACKGROUND

In computer networking, multicast communications are communications in which data is addressed to a multicast group comprising multiple recipients simultaneously. The multicast communications may have either one source (i.e., one-to-many multicast) or multiple sources (i.e., many-to-many multicast). Network assisted multicast is a specific type of multicast communication in which one-to-many addressing and switching is implemented at either the data link layer (e.g., using Ethernet multicast addressing, Asynchronous Transfer Mode (ATM), point-to-multipoint (P2MP) virtual circuits, or Infiniband multicast) or the network layer (e.g., using Internet Protocol (IP) multicast).

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram of an example system of the present disclosure;

FIG. 2 illustrates a flowchart of an example method for enabling multicast forwarding in a wide area network;

FIG. 3 illustrates a flowchart of an example method for joining a host at a branch location in a wide area network to a multicast group;

FIG. 4 illustrates a flowchart of another example method for joining a host at a branch location in a wide area network to a multicast group; and

FIG. 5 depicts a high-level block diagram of an apparatus that can be transformed into a machine capable of performing the functions described herein.

DETAILED DESCRIPTION

The present disclosure broadly discloses a method and non-transitory computer-readable medium for modifying headend forwarding rules to join wide area network branch hosts to multicast groups. As discussed above, multicast communications are network communications in which data is addressed to a multicast group comprising multiple recipients simultaneously. As such, multicast communications may be especially useful in wide area networks (WANs) that connect one or more geographically distributed branches of an enterprise or organization. However, many network devices in a WAN may lack full multicast routing support. It may also be operationally infeasible to deploy multicast routing over the WAN links.

Examples of the present disclosure provide a novel method for deploying multicast forwarding in a software-defined WAN (SD-WAN) without using multicast routing. In one example, the SDN routing application includes a centralized WAN controller, as well as agent controllers that are deployed at both the WAN headend(s) (e.g., an enterprise data center) and WAN branch location(s). When a host device at a branch location wishes to join a multicast group (e.g., as a sender or as a recipient), the centralized WAN controller may modify a forwarding rule associated with an agent controller residing at a WAN headend accordingly. The forwarding rule controls an interaction between the agent controller residing at the headend and an upstream network layer router to redirect multicast traffic associated with the multicast group in a manner that joins the host residing at the branch location to the multicast group. The multicast traffic may comprise a plurality of data packets transmitted in accordance with the Internet Protocol (IP) communications protocol. In one example, the multicast traffic comprises IP version 4 (IPv4) or IP version 6 (IPv6) type traffic; however, in other examples, the multicast traffic may comprise traffic of types associated with other communications protocols, including other versions of IP.

FIG. 1 illustrates an example system 100 of the present disclosure. In one example, the system 100 is deployed in a wide area network (WAN), such as a SD-WAN, and generally includes a centralized WAN controller in communication with a WAN branch location 108 and a WAN headend location 112. It should be noted that although one WAN branch location 108 and one WAN headend location 112 are illustrated in FIG. 1, any number of WAN branch locations and WAN headend locations may be in communication with the centralized WAN controller 102.

The centralized WAN controller 102 executes a routing application 104 that controls the routing of network traffic across the links of a wide area network to the WAN headend location 112. As described in greater detail in connection with FIGS. 2-4, the routing application 104 may be configured to enable multicast forwarding in the WAN without using multicast routing. The routing application 104 may run as a service in a cloud network.

The WAN branch location 108 connects one or more remote host devices, or “hosts” (e.g., including end user computing devices such as desktop computers, laptop computers, tablet computers, Voice over Internet Protocol (VoIP) phones, smart phones, wearable smart devices, and other devices) to the WAN. The WAN branch location 108 includes a first agent controller 106 that may cooperate with the routing application 104 to orchestrate forwarding of network traffic associated with a multicast group to and/or from one of the hosts at the WAN branch location 108.

The WAN headend location 112 aggregates the WAN branch locations, including the WAN branch location 108, into a core WAN router. The WAN headend location 112 includes a second agent controller 110 that may cooperate with the routing application 104 to modify one or more forwarding rules 114. The forwarding rules 114 control interactions between the second agent controller 110 and an upstream router (e.g., a network layer router) to redirect network traffic (e.g., IPv4 or IPv6 data packets) associated with a multicast group in a manner that joins a host at the WAN branch location 108 to the multicast group.

FIG. 2 illustrates a flowchart of an example method 200 for enabling multicast forwarding in a wide area network. In one example, the method 200 may be performed by a centralized WAN controller, such as the centralized WAN controller 102 illustrated in FIG. 1, or by a computer as illustrated in FIG. 5 and discussed below. As such, reference is made in the discussion of the method 200 to various elements of FIG. 1. Such reference is made to facilitate understanding and is not intended to limit the means by which the method 200 may be performed.

At block 202, the method 200 begins. At block 204, the routing application 104 at the centralized WAN controller 102 receives a request from the first agent controller 106. The request requests that a host at the WAN branch location 108 be joined to a multicast group. The host may request to join the multicast group as a receiver (e.g., such that the host serves as a destination for network traffic associated with the multicast group) or as a sender (e.g., such that the host serves as a source for network traffic associated with the multicast group).

In block 206, the routing application 104 sends, in response to the request, an instruction to the second agent controller 110. The instruction instructs the second agent controller 110 to modify a forwarding rule associated with the WAN headend location 112. As discussed above, the forwarding rule may control an interaction between the WAN headend location 112 and an upstream router (e.g., a network layer router) to redirect network traffic (e.g., IPv4 or IPv6 data packets) associated with the multicast group in a manner that joins the host to the multicast group. The specific manner in which the forwarding rule is modified may vary depending on whether the host has requested to join the multicast group as a receiver or as a sender. FIG. 3, for instance, illustrates a more detailed method for joining the host to the multicast group as a receiver, while FIG. 4 illustrates a more detailed method for joining the host to the multicast group as a sender. The centralized WAN controller 102 and/or the routing application 104 may also take additional actions to enable multicast forwarding to and/or from the host depending on whether the host has requested to join the multicast group as a receiver or as a sender.

The method 200 ends in block 208.

FIG. 3 illustrates a flowchart of an example method 300 for joining a host at a branch location in a wide area network to a multicast group. In one example, the method 300 may be performed by a centralized WAN controller, such as the centralized WAN controller 102 illustrated in FIG. 1, or by a computer as illustrated in FIG. 5 and discussed below. As such, reference is made in the discussion of the method 300 to various elements of FIG. 1. Such reference is made to facilitate understanding and is not intended to limit the means by which the method 300 may be performed.

At block 302, the method 300 begins. At block 304, the routing application 104 at the centralized WAN controller 102 receives a request from the first agent controller 106. The request requests that a host at the WAN branch location 108 be joined to a multicast group as a receiver (e.g., such that the host serves as a destination for network traffic associated with the multicast group). The request may also identify WAN headend location 112 as a preferred WAN headend location for the host.

In block 306, the routing application 104 sends an instruction to the second agent controller 110 to send an Internet group management protocol (IGMP) join on behalf of the host. The IGMP join will operate to pull network traffic (e.g., IPv4 or IPv6 data packets) associated with the multicast group towards the WAN headend location 112. In one example, depending on the protocol independent multicast (PIM) mode used in the WAN, the IGMP join may be an IGMPv2 or an IGMPv3 join. Other types of IGMP joins are also possible.

In block 308, the routing application 104 sends an instruction to the second agent controller 110 to modify the forwarding rules 114 at the WAN headend location 112 so that incoming network traffic associated with the multicast group is pushed or redirected by the router(s) at the WAN headend location 112 into a secure tunnel, such as an Internet Protocol security (IPsec) tunnel, toward the WAN branch location 108.

The method 300 ends in block 310.

FIG. 4 illustrates a flowchart of another example method 400 for joining a host at a branch location in a wide area network to a multicast group. In one example, the method 400 may be performed by a centralized WAN controller, such as the centralized WAN controller 102 illustrated in FIG. 1, or by a computer as illustrated in FIG. 5 and discussed below. As such, reference is made in the discussion of the method 400 to various elements of FIG. 1. Such reference is made to facilitate understanding and is not intended to limit the means by which the method 400 may be performed.

At block 402, the method 400 begins. At block 404, the routing application 104 at the centralized WAN controller 102 receives a request from the first agent controller 106. The request requests that a host at the WAN branch location 108 be joined to a multicast group as a sender (e.g., such that the host serves as a source for network traffic associated with the multicast group). The request may also identify WAN headend location 112 as a preferred WAN headend location for the host.

At block 406, the routing application 104 sends an instruction to the first agent controller 106 to redirect network traffic associated with the multicast group and for which the host is the source to the WAN headend location 112.

At block 408, the routing application 104 sends an instruction to the second agent controller 110 to perform network address translation (NAT) for the redirected network traffic to make it appear that the WAN headend location 112 is the source of the redirected network traffic. For instance, the second agent controller 110 may translate the host address on data packets of the redirected network traffic into an address of the WAN headend location's upstream network layer interface. Thus, the first-hop upstream router (e.g., network layer router) beyond the WAN headend location 112, which expects the source of the redirected network traffic to be a directly connected subnet (in order for PIM source registration to work as expected), will view the WAN headend location 112 as the source of the redirected network traffic.

At block 410, the routing application 104 sends an instruction to the second agent controller 110 to modify the forwarding rules 114 at the WAN headend location 112 so that the redirected network traffic is replayed on the upstream network layer interface of the WAN headend location 112. Upstream, regular PIM mechanisms may be used to deliver the redirected network traffic to members of the multicast group. In addition, the modified forwarding rules 114 may replay the redirected network traffic on any secure tunnels, such as IPsec tunnels, toward WAN branch locations (which may or may not include WAN branch location 108) including hosts who are members of the multicast group.

The method 400 ends at block 412.

It should be noted that although not explicitly specified, some of the blocks, functions, or operations of the methods 300 and 400 described above may include storing, displaying and/or outputting for a particular application. In other words, any data, records, fields, and/or intermediate results discussed in the method can be stored, displayed, and/or outputted to another device depending on the particular application. Furthermore, blocks, functions, or operations in FIGS. 3 and 4 that recite a determining operation, or involve a decision, do not necessarily imply that both branches of the determining operation are practiced. Moreover, blocks, functions, or operations of the above described method(s) can be combined, separated, and/or performed in a different order from that described above, without departing from the examples of the present disclosure.

FIG. 5 depicts a high-level block diagram of an apparatus that can be transformed into a machine capable of performing the functions described herein. In one example, the apparatus 500 may be the centralized WAN controller 102 of FIG. 1. In one example, the apparatus 500 may include a processor 502 and a non-transitory computer readable storage medium 504. The non-transitory computer readable storage medium 504 may include instructions 506 and 508 that, when executed by the processor 502, cause the processor 502 to perform various functions.

In one example, the instructions 506 may include instructions to receive a request from a first agent controller at a WAN branch location, where the request requests that a host at the WAN branch location be joined to a multicast group. The instructions 508 may include instructions to send an instruction to a second agent controller at a WAN headend location, where the instruction instructs the second agent controller to modify a forwarding rule that controls an interaction between the WAN headend location and an upstream router to redirect network traffic associated with the multicast group in a manner that joins the host to the multicast group

It will be appreciated that variants of the above-disclosed and other features and functions, or alternatives thereof, may be combined into many other different systems or applications. Various presently unforeseen or unanticipated alternatives, modifications, variations, or improvements therein may be subsequently made by those skilled in the art which are also intended to be encompassed by the following claims. 

What is claimed is:
 1. A system, comprising: a centralized controller executing a routing application to control routing of network traffic across links of a wide area network; a first agent controller deployed at a branch location of the wide area network to notify the routing application when a host at the branch location requests membership in a multicast group; and a second agent controller deployed at a headend of the wide area network to modify a forwarding rule in response to an instruction from the routing application, wherein the forwarding rule controls an interaction between the headend location and an upstream router to redirect network traffic associated with the multicast group in a manner that joins the host to the multicast group.
 2. The system of claim 1, wherein the upstream router is a network layer router.
 3. The system of claim 1, wherein the wide area network is a software-defined wide area network.
 4. The system of claim 1, wherein the interaction joins the host to the multicast group without the use of multicast routing.
 5. The system of claim 1, wherein the routing application runs as a service is a cloud network.
 6. A method, comprising: receiving, by a centralized controller in a wide area network, a request from a first agent controller deployed at a branch location in the wide area network to join a host at the branch location to a multicast group; and sending, by the centralized controller, an instruction to a second agent controller deployed at a headend location in the wide area network to modify a forwarding rule associated with the second agent controller, wherein the forwarding rule controls an interaction between the headend location and an upstream router to redirect network traffic associated with the multicast group in a manner that joins the host to the multicast group.
 7. The method of claim 6, wherein the request requests that the host join the multicast group as a receiver.
 8. The method of claim 7, wherein the instruction to the second agent controller further comprises: an instruction to send a join on behalf of the host to pull the network traffic associated with the multicast group towards the headend location.
 9. The method of claim 8, wherein the join is an internet group management protocol join.
 10. The method of claim 8, wherein a modification made to the forwarding rule in response to the instruction to the second agent controller causes the network traffic associated with the multicast group to be pushed by a router of the headend location into a secure tunnel toward the branch location.
 11. The method of claim 10, wherein the secure tunnel is a internet protocol security tunnel.
 12. The method of claim 6, wherein the request requests that the host join the multicast group as a sender.
 13. The method of claim 12, further comprising: sending, by the centralized controller, an instruction to the first agent controller to redirect the network traffic associated with the multicast group and for which the host is a source to the headend location.
 14. The method of claim 13, wherein the instruction to the second agent controller further comprises: an instruction to perform network address translation for the network traffic associated with the multicast group and for which the host is a source to make it appear that the headend is the source.
 15. The method of claim 14, wherein a modification made to the forwarding rule in response to the instruction to the second agent controller causes the network traffic associated with the multicast group and for which the host is a source to be replayed on an upstream network layer interface of the headend location.
 16. The method of claim 15, wherein the modification further causes the network traffic associated with the multicast group and for which the host is a source to be pushed into a secure tunnel toward a branch location of the wide area network including a host who is a member of the multicast group.
 17. A centralized controller in a wide area network, the centralized controller comprising: a processor; a non-transitory computer readable storage medium to store instructions that, when executed by the processor, cause the processor to perform operations comprising: receiving a request from a first agent controller deployed at a branch location in the wide area network to join a host at the branch location to a multicast group; and sending an instruction to a second agent controller deployed at a headend location in the wide area network to modify a forwarding rule associated with the second agent controller, wherein the forwarding rule controls an interaction between the headend location and an upstream router to redirect network traffic associated with the multicast group in a manner that joins the host to the multicast group.
 18. The centralized controller of claim 17, wherein the request requests that the host join the multicast group as a receiver, and the instruction to the second agent controller comprises: an instruction to send a join on behalf of the host to pull the network traffic associated with the multicast group towards the headend location; and an instruction to push, by a router of the headend location, the network traffic associated with the multicast group into a secure tunnel toward the branch location.
 19. The centralized controller of claim 17, wherein the request requests that the host join the multicast group as a sender, and the operations further comprise: sending an instruction to the first agent controller to redirect the network traffic associated with the multicast group and for which the host is a source to the headend location.
 20. The centralized controller of claim 19, wherein the instruction to the second agent controller comprises: an instruction to perform network address translation for the network traffic associated with the multicast group and for which the host is a source to make it appear that the headend is the source; and an instruction to replay the network traffic associated with the multicast group and for which the host is a source on an upstream network layer interface of the headend location. 